Will be fixing the lint test errors, could I get some leads on how to fix the Roboelectric tests? They are giving the following outputs:

Execution failed for task ':app:mergeDebugJavaResource'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not download byte-buddy.jar (net.bytebuddy:byte-buddy:1.6.11)
      > Could not get resource 'https://jcenter.bintray.com/net/bytebuddy/byte-buddy/1.6.11/byte-buddy-1.6.11.jar'.
         > Could not GET 'https://d29vzk4ow07wi7.cloudfront.net/(long URL)'
            > Connection reset

> Task :app:kaptGenerateStubsDebugKotlin FAILED
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:kaptGenerateStubsDebugKotlin'.
> Could not resolve all artifacts for configuration ':app:debugCompileClasspath'.
   > Could not download mockito-core.jar (org.mockito:mockito-core:2.7.22)
      > Could not get resource 'https://jcenter.bintray.com/org/mockito/mockito-core/2.7.22/mockito-core-2.7.22.jar'.
         > Could not GET '(LONG URL)'
            > Connection reset

@Arjupta @prayutsu would you like to help the contributor here with few initial thoughts on this.

@navneetsaluja Check our wiki guide here for ktlint issues - https://github.com/oppia/oppia-android/wiki/Ktlint-Guide

Will be fixing the lint test errors, could I get some leads on how to fix the Roboelectric tests? They are giving the following outputs:

Execution failed for task ':app:mergeDebugJavaResource'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not download byte-buddy.jar (net.bytebuddy:byte-buddy:1.6.11)
      > Could not get resource 'https://jcenter.bintray.com/net/bytebuddy/byte-buddy/1.6.11/byte-buddy-1.6.11.jar'.
         > Could not GET 'https://d29vzk4ow07wi7.cloudfront.net/(long URL)'
            > Connection reset

> Task :app:kaptGenerateStubsDebugKotlin FAILED
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:kaptGenerateStubsDebugKotlin'.
> Could not resolve all artifacts for configuration ':app:debugCompileClasspath'.
   > Could not download mockito-core.jar (org.mockito:mockito-core:2.7.22)
      > Could not get resource 'https://jcenter.bintray.com/org/mockito/mockito-core/2.7.22/mockito-core-2.7.22.jar'.
         > Could not GET '(LONG URL)'
            > Connection reset

Have you tried this after connecting to internet?

@anandwana001 Thank you!

@Arjupta

Have you tried this after connecting to internet?

I'm not sure what you mean. All these tests were done on Github while pushing (here). Other than that, my local instance is always connected to the internet.

@anandwana001 Thank you!

@Arjupta

Have you tried this after connecting to internet?

I'm not sure what you mean. All these tests were done on Github while pushing (here). Other than that, my local instance is always connected to the internet.

I think you should run these tests once again. So just make a commit after correcting the lint error, it will automatically trigger the tests

Hi @navneetsaluja
I think this classifier is not about uppercase and lowercase strings. You should take a look at ItemSelectionContainsAtLeastOneOfRule and then try figuring out what you need to do.
ItemSelectionContainsAtLeastOneOfRule
Also, remove the TODO in the file ItemSelectionContainsAtLeastOneOfRule

Will be fixing the lint test errors, could I get some leads on how to fix the Roboelectric tests? They are giving the following outputs:

Execution failed for task ':app:mergeDebugJavaResource'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not download byte-buddy.jar (net.bytebuddy:byte-buddy:1.6.11)
      > Could not get resource 'https://jcenter.bintray.com/net/bytebuddy/byte-buddy/1.6.11/byte-buddy-1.6.11.jar'.
         > Could not GET 'https://d29vzk4ow07wi7.cloudfront.net/(long URL)'
            > Connection reset

> Task :app:kaptGenerateStubsDebugKotlin FAILED
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:kaptGenerateStubsDebugKotlin'.
> Could not resolve all artifacts for configuration ':app:debugCompileClasspath'.
   > Could not download mockito-core.jar (org.mockito:mockito-core:2.7.22)
      > Could not get resource 'https://jcenter.bintray.com/org/mockito/mockito-core/2.7.22/mockito-core-2.7.22.jar'.
         > Could not GET '(LONG URL)'
            > Connection reset

These tests are giving this error because these are not relevant to this particular classifier, in this test we want to test if the inputs and answer have any common item or not. And that's what the name suggests, "contains at least one" (answer should contain at least one of the item in inputs).

@navneetsaluja You can do one more thing, you can add keywords Fixes #bugnum in the explanation section itself and not above the explanation section, then this would be more close to our conventional PR description

@Arjupta Will commit again once I implement prayutsu's suggestions. Thank you.

@prayutsu I see, I already have three tests in mind, will try implementing them. Will edit the description of the PR as well to suit the conventions. Thank you for your input!

Thanks a lot @prayutsu and @Arjupta for helping out new contributors. Thanks a lot.

@prayutsu @Arjupta PTAL, checks passed, thanks.
Updated the tests too: they use a common Item Set as answer which is
["test1","test2","test3","test4","test5"]
I feel that the variables and the functions have bad names - not sure what to name them. Any more ideas for tests would also be helpful. Thanks!

@prayutsu @Arjupta PTAL, checks passed, thanks.
Updated the tests too: they use a common Item Set as answer which is
["test1","test2","test3","test4","test5"]
I feel that the variables and the functions have bad names - not sure what to name them. Any more ideas for tests would also be helpful. Thanks!

Changes I mentioned are done correctly. LGTM Thanks @navneetsaluja

@navneetsaluja I think variable names are fine, but I am not sure about the test case names, maybe @anandwana001 can suggest some good name.

@navneetsaluja It would be more close to our conventional title for the PRs if you add a colon after Fixes #bugnum like this Fixes #1896:
Also, it's good to have the PR title the same as the issue name.

@prayutsu I see, will take care of it in future PRs. Thanks.

@prayutsu new commit, PTAL :)

@Arjupta @prayutsu please resolve your comments, if you think the required changes are made.

@anandwana001 i think only the author of PR and people with write access can resolve them, as I am unable to find the resolve conversation button

@Arjupta @prayutsu please resolve your comments, if you think the required changes are made.

Actually, I am not getting the option to resolve comments.

@Arjupta @prayutsu oh, ok, I got it. Thanks for update. The author will resolve it.

@/anandwana001(Not pinging because you've already been assigned)
Sorry for the late update, had real life commitments. Was thinking of using the createListOfSetsOfHtmlStrings defined in the InteractionObjectTestBuilder.kt but then it was rendering code a bit unreadable, so I just shifted my function to InteractionObjectTestBuilder.kt.
Other than that, it gives an App module test error here:
Caused by: org.gradle.process.internal.ExecException: Process 'Gradle Test Executor 15' finished with non-zero exit value 134 This problem might be caused by incorrect test process configuration.
; but on my local machine all the tests passed.

UPDATE: Checks passed now, I didn't change anything. When I wrote the original comment it was displaying the error above.

@anandwana001 Added screenshot!